Service management system and non-transitory computer readable medium

ABSTRACT

A service management system manages use authority for service information, the service information including a content of a service to be provided to a user of a vehicle, the service management system includes a memory configured to store a user ID given for each user of the vehicle and service information set for each vehicle, the user ID and the service information being associated with each other, and a processor configured to unify the use authority for first service information when a plurality of pieces of service information is associated with a single user ID, the first service information being included in each piece of service information.

INCORPORATION BY REFERENCE

This application is a continuation of U.S. patent application Ser. No.16/274,571, filed Feb. 13, 2019, which claims priority Japanese PatentApplication No. 2018-040932, filed on Mar. 7, 2018, including thespecification, drawings and abstract is incorporated herein by referencein its entirety.

BACKGROUND 1. Technical Field

The disclosure relates to a service management system that manages useauthority for a service to be provided to a user of a vehicle, for eachuser, and a non-transitory computer readable medium.

2. Description of Related Art

In a system described in Japanese Patent Application Publication No.2006-4180 (JP 2006-4180 A), a shop-side terminal is communicablyconnected to a vehicle and a user terminal, and communication betweenthe user terminal and the vehicle is authenticated based on personalauthentication information registered in the shop-side terminal. In thesystem, a person ID, a vehicle ID and a user terminal ID are associatedwith each other in a customer database server that is managed by theshop-side terminal. For example, using vehicle information such as a usehistory and repair history of the vehicle, the shop-side terminalprovides a service appropriate to the vehicle, as exemplified byperiodic inspection for oil change, to the user terminal correspondingto the user ID associated with the vehicle ID. Further, for example,using personal information such as a sexuality, age and non-accidenthistory of a person, the shop-side terminal provides a serviceappropriate to the person, to the user terminal corresponding to theuser terminal ID associated with the person ID.

SUMMARY

In the system described in JP 2006-4180 A, the vehicle ID and the personID are associated with each other, and the service appropriate to theperson is provided based on characteristics of the user corresponding tothe person ID. Therefore, when a single user possesses a plurality ofvehicles, it is necessary to manage use authority for the serviceappropriate to the person, for each vehicle, and there is still room forimprovement in the management of the use authority for the service.

The disclosure provides a service management system that can manage theuse authority for the service to be provided to the user of the vehicle,for each user, and a non-transitory computer readable medium.

A service management system of the disclosure is a service managementsystem that manages use authority for service information, the serviceinformation including a content of a service to be provided to a user ofa vehicle, the service management system including: a memory configuredto store a user ID given for each user of the vehicle and serviceinformation set for each vehicle, the user ID and the serviceinformation being associated with each other; and a processor configuredto unify the use authority for first service information when aplurality of pieces of service information is associated with a singleuser ID, the first service information being included in each piece ofservice information.

A non-transitory computer readable medium of the disclosure is anon-transitory computer readable medium storing a program causing acomputer to perform a process, the computer including a memoryconfigured to store a user ID given for each user of a vehicle andservice information, the service information including a content of aservice to be provided to the user of the vehicle, the user ID and theservice information being associated with each other, the processincluding unifying use authority for first service information when aplurality of pieces of service information is associated with a singleuser ID, the first service information being included in each piece ofservice information.

With the above aspect, when a single user possesses a plurality ofvehicles, the use authority for the service information corresponding tothe vehicles associated with a single user ID is shared. Therefore, itis possible to manage the use authority for the service to be providedto the user of the vehicle, for each user, with a high convenience.

In the service management system, the service information may furtherinclude second service information for which the use authority is linkedwith the vehicle, in addition to the first service information for whichthe use authority is linked with the user; and the processor may beconfigured not to unify the use authority for the second serviceinformation, while unifying the use authority for the first serviceinformation.

With this configuration, even when a single user possesses a pluralityof vehicles, the use authority is not unified for the second serviceinformation for which the use authority is linked with the vehicle.Therefore, even when a plurality of users shares a single vehicle, it ispossible to prevent an unrighteous use of the service for which the useauthority is linked with the vehicle.

In the service management system, the memory may be configured to storea plurality of user IDs associated with common service information; andthe processor may be configured to manage the use authority for thefirst service information for each user ID, and manage the use authorityfor the second service information in common among the plurality of userIDs, when the processor manages the use authority for the common serviceinformation.

With this configuration, even when a plurality of users shares a singlevehicle, the second service information set for the vehicle is applied.Therefore, it is possible to simplify the setting of the second serviceinformation, compared to when the second service informationcorresponding to the users is set for the vehicle.

In the service management system, the use authority for the firstservice information may include an expiration date of the first serviceinformation; and the processor may be configured to apply a latestexpiration date of a plurality of expiration dates of the first serviceinformation, to other expiration dates of the first service information.

With this configuration, when a single user possesses a plurality ofvehicles, the expiration dates of the first service informationcorresponding to the vehicles are unified to the latest expiration date.Therefore, the user can manage a plurality of service expiration dates,with a high convenience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, advantages, and technical and industrial significance ofexemplary embodiments of the disclosure will be described below withreference to the accompanying drawings, in which like numerals denotelike elements, and wherein:

FIG. 1 is a block diagram showing a schematic configuration of anembodiment of a service management system;

FIG. 2 is a schematic diagram showing exemplary data contents stored indata tables;

FIG. 3 is a schematic diagram showing an exemplary association of avariety of information with a user ID;

FIG. 4 is a schematic diagram showing an exemplary classification ofservices to be provided to a user of a vehicle;

FIG. 5 is a schematic diagram showing an exemplary data content oflicense information;

FIG. 6A is a schematic diagram showing an exemplary association of avariety of information with the user ID;

FIG. 6B is a schematic diagram showing an exemplary association of avariety of information with the user ID;

FIG. 6C is a schematic diagram showing an exemplary association of avariety of information with the user ID;

FIG. 7 is a schematic diagram showing a process flow in an initialregistration of a variety of information associated with the licenseinformation; and

FIG. 8 is a sequence chart showing a service management process that isexecuted by the service management system in the embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

Hereinafter, an embodiment of a service management system will bedescribed with reference to the drawings. The service management systemin the embodiment is a system that manages service information (licenseinformation) when a user of a vehicle uses a service of an applicationusing the vehicle. In this system, a portable information terminal(communication device) held by the user of the vehicle is configured tobe capable of communicating with the vehicle, and a vehicle ID that isobtained by the communication with the vehicle and a user ID that isidentification information of the user holding the portable informationterminal are sent to a data center that manages a plurality of pieces ofvehicle information. When the data center receives the vehicle ID andthe user ID from the portable information terminal, the data centerreads license information associated with the vehicle ID and the userID, from a memory. Then, the data center returns the read licenseinformation to the portable information terminal as the sending source.Thereby, use in the portable information terminal of the service usingthe vehicle is managed.

Specifically, as shown in FIG. 1 , the portable information terminal 100includes a processor 110, a memory 120, a communication module 130, anoperation part 140 and a display 150. The processor 110 integrallycontrols behavior of the portable information terminal 100, and canexecute a variety of application 121 including an application using thevehicle.

The memory 120 stores a user ID 122 that is identification informationof the user holding the portable information terminal 100, in additionto the variety of application 121. As the user ID 122, for example, anemail address of the portable information terminal 100 is used.

The communication module 130 performs wireless communication such asBluetooth®, with a vehicle 200, for example. By establishing wirelesscommunication with the vehicle 200, the communication module 130receives a vehicle ID 123 that is identification information of thevehicle 200, from the vehicle 200, and stores the vehicle ID 123 in thememory 120.

The operation part 140 and the display 150 function as user interfaceswhen the user operates the portable information terminal 100. Theoperation part 140 is a push-button operation switch, for example, andoutputs an operation signal to the processor 110. When the display 150is constituted by a touch panel display, the display 150 functions alsoas the operation part 140.

Meanwhile, a data center 300 includes a processor 310, a memory 320 anda communication module 330. The processor 310 integrally controlsbehavior of the data center 300, and functions as a service manager 311that manages use in the portable information terminal 100 of theapplication 121 using the vehicle in response to a request from theportable information terminal 100.

In the memory 320, a variety of data to be used when the service manager311 manages the use of the application 121 is stored. Examples of thevariety of data include a terminal information table 321, a userinformation table 322, a license code table 323 and a vehicleinformation table 324.

When the service manager 311 receives the user ID 122 and the vehicle ID123 from the portable information terminal 100 through the communicationmodule 130, the service manager 311 refers to the tables 321 to 324stored in the memory 320, and extracts license information when the useruses the application 121 using the vehicle 200, based on the user ID 122and the vehicle ID 123. The service manager 311 sends the extractedlicense information from the communication module 330 to the portableinformation terminal 100 as the sending source of the user ID 122 andthe vehicle ID 123. Thereby, the use of the application 121 in theportable information terminal 100 is managed based on the licenseinformation.

More specifically, as shown in FIG. 2 , in the terminal informationtable 321, a telephone number of the portable information terminal 100,and the like are stored, using the terminal ID that is individualinformation of the portable information terminal 100, as a key.

In the user information table 322, a password to be used forauthentication of the user ID 122, user information about the user suchas a user name, user personal information including service use historyinformation, an expiration date of a navigation service based on theuser ID 122, and the like are stored, using the user ID 122 receivedfrom the portable information terminal 100 by the data center 300, as akey.

In the license code table 323, an expiration date of a license code thatis an identification number of the license information, licenserestriction information such as the number of users able to use thelicense and expiration dates of a navigation service based on thelicense code and a service using a data communication module (DCM)mounted on the vehicle, license contractor information, managerinformation about the vehicle that is a license object, and the like arestored, using the license code as a key.

In the vehicle information table 324, traveling history information suchas a traveling distance of the vehicle, in-vehicle device informationsuch as a serial number of the DCM, and the like are stored, using avehicle identification number (VIN) that is an identification number ofthe vehicle, as a key.

Further, the terminal information table 321 and the user informationtable 322 are associated with each other, based on the terminal ID andthe user ID 122 as the respective keys. On this occasion, a plurality ofterminal IDs can be associated with a single user ID. That is, when theuser holds a plurality of portable information terminals 100, aplurality of terminal information tables 321 different corresponding tothe plurality of portable information terminals 100 is associated with acommon user information table 322.

Further, the user information table 322 and the license code table 323are associated with each other, based on the user ID 122 and the licensecode as the respective keys. On this occasion, a plurality of licensecodes can also be associated with a single user ID. That is, when theuser has licenses for a plurality of vehicles, the license code table323 different for each vehicle is associated with a common userinformation table 322. Further, a plurality of user IDs 122 can also beassociated with a single license code. That is, when a license for anidentical vehicle is shared by a plurality of users, the userinformation table 322 different for each user is associated with acommon license code table 323.

Further, the license code table 323 and the vehicle information table324 are associated with each other, based on the license code and VIN asthe respective keys. On this occasion, a single VIN can be associatedwith a single license code. That is, the license information to beapplied to an identical vehicle is common information, and the licensecode table 323 and the vehicle information table 324 have a one-to-onecorrespondence relation.

Accordingly, as shown in FIG. 3 , the user information about the user,the use history information about the service, the terminal informationabout the portable information terminal 100, and the license code areassociated with a single user ID. On this occasion, the user ID and theuser information about the user have a one-to-one correspondencerelation, and the user ID and the use history information about theservice have a one-to-one correspondence relation. In contrast, aplurality of pieces of terminal information can be associated with asingle user ID, and there is no upper limit on the number of pieces ofterminal information as the object. Further, a plurality of licensecodes can be associated to a single user ID, but there is an upper limiton the number of license codes as the object (for example, the upperlimit is five).

Further, the vehicle information, the expiration dates of the navigationservices and the DCM, the manager information about the vehicle as theobject of the license, and the contractor information about the serviceusing the DCM are associated with a single license code. On thisoccasion, each piece of the above-described information has a one-to-onecorrespondence relation with the single license code.

As shown in FIG. 4 , the service to be provided to the user of thevehicle is classified into a person-relevant service that is relevant tothe user and a vehicle-relevant service that is relevant to the vehicle.The person-relevant service is a service for which the use authority islinked with the user, and is classified into a navigation service usingthe portable information terminal 100 held by the user and otherservices. The vehicle-relevant service is a service for which the useauthority is linked with the vehicle, and is classified into a serviceusing the DCM mounted on the vehicle and a service not using the DCM.Each of the classified services includes a fee-based service and a freeservice.

As shown in FIG. 5 , in addition to the number of users able to use thelicense, as described above, the license information includes licenseinformation about the person-relevant service and license informationabout the vehicle-relevant service. In an example shown in FIG. 5 , thelicense information about the person-relevant service includes theexpiration date of the navigation service using the portable informationterminal 100 and the expiration dates of other paid contents. In thisexample, the license information about the vehicle-relevant serviceincludes the expiration date of a basic service using the DCM and theexpiration dates of optional service using the DCM.

Next, a manner of setting of the license information to the applicationwhen the user holding the portable information terminal 100 uses thevehicle 200 will be described with specific examples. In an exampleshown in FIG. 6A, the number of object users is one (“USER A”), and thenumber of object vehicles is one (“VEHICLE 1”). In this example, alicense code (“111”) corresponding to “VEHICLE 1” is associated with theuser ID (“USERA@ . . . ”) corresponding to “USER A”. The navigationexpiration date (“20/12/31”) and DCM expiration date (“17/12/31”) for“VEHICLE 1” are associated with the license code (“111”). In this case,the navigation expiration date for “USER A” is set to “20/12/31”. TheDCM expiration date for “USER A” is set to “17/12/31”.

In an example shown in FIG. 6B, the number of object users is one (“USERA”), and the number of object vehicles is two (“VEHICLE 1”, “VEHICLE2”). In this example, the license code (“111”) corresponding to “VEHICLE1” and a license code (“222”) corresponding to “VEHICLE 2” areassociated with the user ID (“USERA@ . . . ”) corresponding to “USER A”.The navigation expiration date (“20/12/31”) and DCM expiration date(“17/12/31”) for “VEHICLE 1” are associated with the license code(“111”). The navigation expiration date (“19/12/31”) and DCM expirationdate (“18/12/31”) for “VEHICLE 2” are associated with the license code(“222”). In this case, the navigation expiration date for “USER A” isset to the latest navigation expiration date (“20/12/31”) of thenavigation expiration date (“20/12/31”) for “VEHICLE 1” and thenavigation expiration date (“19/12/31”) for “VEHICLE 2”. As the DCMexpiration date for “USER A”, the DCM expiration date (“17/12/31”) isset for “VEHICLE 1”, and the DCM expiration date (“18/12/31”) is set for“VEHICLE 2”. That is, the navigation expiration date for which the useauthority is linked with the user is unified, but the DCM expirationdate for which the use authority is linked with the vehicle is notunified.

In an example shown in FIG. 6C, the number of object users is two (“USERA”, “USER B”), and the number of object vehicles is two (“VEHICLE 1”,“VEHICLE 2”). In this example, the license code (“111”) corresponding to“VEHICLE 1” and a license code (“222”) corresponding to “VEHICLE 2” areassociated with the user ID (“USERA@ . . . ”) corresponding to “USER A”.The license code (“222”) corresponding to “VEHICLE 2” is associated withthe user ID (“USERB@ . . . ”) corresponding to “USER B”. The navigationexpiration date (“20/12/31”) and DCM expiration date (“17/12/31”) for“VEHICLE 1” are associated with the license code (“111”). The navigationexpiration date (“19/12/31”) and DCM expiration date (“18/12/31”) for“VEHICLE 2” are associated with the license code (“222”). In this case,the navigation expiration date for “USER A” is set to the latestnavigation expiration date (“20/12/31”) of the navigation expirationdate (“20/12/31”) for “VEHICLE 1” and the navigation expiration date(“19/12/31”) for “VEHICLE 2”. The navigation expiration date for “USERB” is set to the navigation expiration date (“19/12/31”) for “VEHICLE2”. That is, when a plurality of user IDs is associated with a commonlicense code, the navigation expiration date for which the use authorityis linked with the user is managed for each user ID. As the DCMexpiration date for “USER A”, the DCM expiration date (“17/12/31”) isset for “VEHICLE 1”, and the DCM expiration date (“18/12/31”) is set for“VEHICLE 2”. On the other hand, as the DCM expiration date for “USER B”,the DCM expiration date (“18/12/31”) for “VEHICLE 2” is set. That is,when a plurality of user IDs is associated with a common license code,the DCM expiration date for which the use authority is linked with thevehicle is managed in common among the plurality of user IDs.

Next, a process flow in an initial registration of a variety ofinformation associated with the license information will be described.As shown in FIG. 7 , in the initial registration of the variety ofinformation, first, the application 121 is started by operating theoperation part 140 of the portable information terminal 100.

Then, an initial screen of the application 121 is displayed on thedisplay 150 of the portable information terminal 100. When the initialregistration of the user ID is selected on the initial screen, an inputscreen for the license code is displayed on the display 150.

Subsequently, when the license code is input through the operation part140, a code authentication of the license code is performed. The codeauthentication is performed by whether the input license code coincideswith one of the license codes registered in the license code table 323.Then, when the code authentication succeeds, a creation screen for theuser ID is displayed on the display 150.

When the user ID and the password are input through the operation part140 on the creation screen for the user ID, an input screen for the userinformation is displayed on the display 150. When the user name and thetelephone number of the portable information terminal 100 are inputthrough the operation part 140 on the input screen for the userinformation, a screen for terms of service about the application 121 isdisplayed on the display 150.

When an operation for agreement is input through the operation part 140on the screen for terms of service, a providing screen for the serviceusing the application 121 is displayed on the display 150. In this case,on the providing screen, services that the license information permitsto be executed are displayed, but services that the license informationprohibits from being executed are not displayed. That is, the use of theservice using the application 121 is managed based on the licenseinformation.

Next, a service management process that is executed by the servicemanagement system in the embodiment will be described. As shown in FIG.8 , in the embodiment, as a premise, when the communication between thevehicle 200 and the portable information terminal 100 is established bywireless communication, the vehicle ID 123 of the vehicle 200 is setfrom the vehicle 200 to the portable information terminal 100. At thistime, the portable information terminal 100 stores the vehicle ID 123received from the vehicle 200, in the memory 120.

When the service is provided to the user of the vehicle, the user,first, starts the application 121 mounted on the portable informationterminal 100 held by the user. At this time, in connection with thestart of the application 121, the input screen for the user ID 122 isdisplayed on the display 150 of the portable information terminal 100.

Then, when the user ID 122 is input through the operation part 140 ofthe portable information terminal 100, the input user ID 122 is sentfrom the portable information terminal 100 to the data center 300. Atthis time, the data center 300 performs the authentication process forthe user ID 122 input from the portable information terminal 100. Whenthe authentication process by the data center 300 succeeds, the portableinformation terminal 100 reads the vehicle ID 123 stored in the memory120, and sends the vehicle ID 123 to the data center 300.

Then, based on the user ID 122 and vehicle ID 123 input from theportable information terminal 100, the data center 300 refers to theuser information table 322, the license code table 323 and the vehicleinformation table 324, and extracts the license informationcorresponding to the combination of the user ID 122 and the vehicle ID123, from the license code table 323.

More specifically, the data center 300 refers to the user informationtable 322 and the license code table 323, and extracts a single or aplurality of license codes associated with the user ID 122. When only asingle license code is associated with the user ID 122, the data center300 extracts the license information corresponding to the combination ofthe user ID 122 and the vehicle ID 123, from the license code table 323,based on the license code. On the other hand, when a plurality oflicense codes is associated with the user ID 122, the data center 300selects the license code associated with the vehicle ID 123, from theplurality of license codes. Based on the selected license code, the datacenter 300 extracts the license information corresponding to thecombination of the user ID 122 and the vehicle ID 123, from the licensecode table 323. Then, the data center 300 sends the license informationextracted from the license code table 323, to the portable informationterminal 100.

Thereafter, based on the license information received from the datacenter 300, the portable information terminal 100 displays the providingscreen for the service of the application 121 in which the use isrestricted, on the display 150. At this time, the portable informationterminal 100 performs the synchronization of the display informationwith an in-vehicle device mounted on the vehicle 200. Therefore, on thein-vehicle device mounted on the vehicle 200, the providing screen forthe service of the application 121 in which the use is restricted basedon the above-described license information is displayed, similarly tothe portable information terminal 100.

As described above, with the above embodiment, it is possible to obtainthe following effects. When a single user possesses a plurality ofvehicles 200, the use authority for the license code corresponding tothe vehicles 200 associated with a single user ID is shared. Therefore,it is possible to manage the use authority for the service to beprovided to the user of the vehicle 200, for each user, with a highconvenience.

When a single user possesses a plurality of vehicles 200, the DCMexpiration date for which the use authority is linked with the vehicle200 is excluded from the object for which the use authority for thelicense code is shared. Therefore, even when a plurality of users sharesa single vehicle 200, it is possible to prevent an unrighteous use ofthe service that uses the DCM and for which the use authority is linkedwith the vehicle 200.

When a plurality of user IDs is associated with a common license codeand the use authority for the license code is managed, the navigationexpiration date for which the use authority is linked with the user ismanaged for each user ID, and the DCM expiration date for which the useauthority is linked with the vehicle is managed in common among theplurality of user IDs. Thereby, even when a plurality of users shares asingle vehicle 200, the DCM expiration date set for the vehicle 200 isapplied. Therefore, it is possible to simplify the setting of the DCMexpiration date, compared to when the DCM expiration date correspondingto the users is set for the vehicle 200.

When a single user possesses a plurality of vehicles 200, the expirationdates of the license codes corresponding to the vehicles 200 are unifiedto the latest expiration date. Therefore, the user can manage aplurality of service expiration dates, with a high convenience.

The above embodiment may be modified to be carried out as follows. Inthe above embodiment, when a plurality of users shares a single vehicle200, the DCM expiration date set for the vehicle 200 is applied.Instead, when a plurality of users shares a single vehicle 200, the DCMexpiration date for each user may be set for the vehicle 200.

In the above embodiment, when a single user possesses a plurality ofvehicles 200, the DCM expiration date for which the use authority islinked with the vehicle 200 is excluded from the object for which theuse authority for the license code is shared. However, the DCMexpiration date for which the use authority is linked with the vehicle200 may be applied as the object for which the use authority for thelicense code is shared.

In the above embodiment, as the use authority for the service, the useterm for the service is specified. However, the use authority for theservice is not limited to the use term for the service, and for example,may be the number of times of use of the service, a period of time ofuse of the service, or an area of use of the service.

In the above embodiment, the data center 300 refers to the userinformation table 322 and the license code table 323, and extracts thelicense code associated with the user ID. Then, when a plurality oflicense codes is associated with the user ID, the data center 300selects the license code associated with the vehicle ID 123, from theplurality of license codes. Instead, the data center 300 may refer tothe vehicle information table 324, and may extract the license codeassociated with the vehicle ID 123. Then, the data center 300 may readthe license information corresponding to the extracted license code,with the condition that the extracted license code is associated withthe user ID 122.

In the above embodiment, the portable information terminal 100 tocommunicate with the vehicle 200 requests the license information to thedata center 300. However, when an in-vehicle device such as a navigationdevice mounted on the vehicle 200 has a communication function, thein-vehicle device may directly request the license information to thedata center 300.

What is claimed is:
 1. A service management system comprising: a memoryconfigured to store service information that includes first serviceinformation for which use authority is linked with a user and secondservice information for which the use authority is linked with avehicle, and a processor configured to unify the use authority for thefirst service information when a plurality of pieces of serviceinformation is associated with a single user ID, the first serviceinformation being included in each piece of service information, whereinthe processor is configured not to unify the use authority for thesecond service information, while unifying the use authority for thefirst service information.
 2. The service management system according toclaim 1, wherein: the memory is configured to store a plurality of userIDs associated with common service information; and the processor isconfigured to manage the use authority for the first service informationfor each user ID, and manage the use authority for the second serviceinformation in common among the plurality of user IDs, when theprocessor manages the use authority for the common service information.3. The service management system according to claim 1, wherein: the useauthority for the first service information includes an expiration dateof the first service information; and the processor is configured toapply a latest expiration date of a plurality of expiration dates of thefirst service information, to other expiration dates of the firstservice information.
 4. A non-transitory computer readable mediumstoring a program causing a computer to perform a process, the computerincluding a memory configured to store service information that includesfirst service information for which use authority is linked with a userand second service information for which the use authority is linkedwith a vehicle, the process comprising unifying use authority for thefirst service information when a plurality of pieces of serviceinformation is associated with a single user ID, the first serviceinformation being included in each piece of service information, whereinthe process is configured not to unify the use authority for the secondservice information, while unifying the use authority for the firstservice information.
 5. The non-transitory computer readable mediumaccording to claim 4, wherein: the memory is configured to store aplurality of user IDs associated with common service information; andthe process is configured to manage the use authority for the firstservice information for each user ID, and manage the use authority forthe second service information in common among the plurality of userIDs, when the process manages the use authority for the common serviceinformation.
 6. The non-transitory computer readable medium according toclaim 4, wherein: the use authority for the first service informationincludes an expiration date of the first service information; and theprocess is configured to apply a latest expiration date of a pluralityof expiration dates of the first service information, to otherexpiration dates of the first service information.